Skip to content

fix(ci): update i18n source hashes after en-US setting.ts change#1928

Closed
HandSonic wants to merge 1 commit into
OtterMind:mainfrom
HandSonic:fix/i18n-hash-update
Closed

fix(ci): update i18n source hashes after en-US setting.ts change#1928
HandSonic wants to merge 1 commit into
OtterMind:mainfrom
HandSonic:fix/i18n-hash-update

Conversation

@HandSonic

Copy link
Copy Markdown
Contributor

Summary

Commit 1e99ff8 changed the baseUrlTip text in en-US/setting.ts but did not update i18n-source-hashes.json. This causes all CI runs to fail with:

es-ES/setting.ts: English source changed; update the translation and its source hash
ko-KR/setting.ts: English source changed; update the translation and its source hash

The es-ES and ko-KR translations were already updated in the same commit, so only the hash file needs updating.

@HandSonic
HandSonic force-pushed the fix/i18n-hash-update branch from 5b3ecfb to 514f38f Compare July 22, 2026 03:19
Commit 1e99ff8 changed the baseUrlTip text in en-US/setting.ts but
did not update i18n-source-hashes.json, causing all CI runs to fail
with 'English source changed; update the translation and its source hash'.
@HandSonic
HandSonic force-pushed the fix/i18n-hash-update branch from 514f38f to 7702381 Compare July 22, 2026 03:25
@openai0229

Copy link
Copy Markdown
Contributor

Thanks for the contribution. The target setting.ts source hash is already present on the current main (b5d94e85d81c95e654f89f9ecc7881b21711a38138f115a27fb79664cb68990a). The remaining common.ts hash differences are only stale baseline differences after later main-branch changes.

There is no longer a valid net fix to merge from this branch, so I am closing this PR as obsolete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants